Search This CD Index Contact Us
Home > Administration > ADAP > Troubleshooting ADAP
| Troubleshooting ADAP
> Establishing a connection to the system Terminating the connection to the system Retrieving data during peak usage Interactions between Terminals on AUDIX systems Timeouts Data Acquisition problems Alogin problems Common problems and solutions This topic provides additional information not found in the command descriptions about error messages and possible abnormal output from the AUDIX Administration and Data Acquisition Package (ADAP) commands. ### Establishing a connection to the system We recommend that you use a Terminal Emulator to debug your modem connection between the INTUITY AUDIX system and your personal computer. ### Terminating the connection to the system If you find that the connection to the voice mail system is not being dropped after the logout command has been issued, check the option switches on your modem. The logout command makes sure that the DTR (data terminal ready) lead on the modem cable is held low for 500 msec. This is long enough for most modems to drop the connection. ### Retrieving data during peak usage Avoid collecting traffic and subscriber data when many users are logged in to the voice mail system. It is best to collect these files after prime time hours. For a given number of subscribers, collection may take more than twice as long when traffic is heavy as it does when traffic is light. ### Interactions between Terminals on AUDIX systems You should be aware of the fact that activity on the maintenance terminal can affect the behavior of data retrievals from the administration port. The operations that are most sensitive to these interactions are retrieval of error and alarm log data. For example, a person on the maintenance terminal can change the error log search specification that was just sent by ADAP using the geterror command. This will result in erroneous data being returned. ### Timeouts The voice mail system will drop terminal sessions after one hour of inactivity. If this occurs before you have finished, you must log in again. ### Data Acquisition problems There are two types of error messages that you might see — fatal and nonfatal. As you would expect, fatal messages are displayed just before the command you are executing quits. After six nonfatal errors when connected to an AUDIX system, ADAP commands will quit. Examples of fatal and nonfatal errors follow: Fatal: If you don't specify a day or month after the -f flag, you will receive a fatal error. Nonfatal: If you specify an invalid extension while using the gettraf command, you will receive a nonfatal error. One class of errors is associated with improper command syntax. These error messages are self explanatory. A table describing driver errors is shown in Converting RS-232 Driver Errors for ADAP. Most protocol errors are recoverable; they indicate that the protocol is recovering from a noise hit on the line. If you see an error message that indicates a protocol error: log out, log in again, and repeat the command. If the same error occurs, get a printout of the error (if possible) and call your remote maintenance service center. ### Alogin (Automated Login) problems To use alogin, make sure that your configuration complies with the guidelines described in Installating ADAP. If the alogin command does not make a successful connection, include the -v flag the next time you run the command. This option (the verbose flag) will display on the screen all input that alogin is sending to the voice mail system, and all of the system's responses. The most common error is due to an invalid login name/password/system password being specified on the alogin command line. ### Common problems and solutions Listed on the following pages are typical problems that you may encounter, along with their solutions. #### Connection problems with login commands:
> Problem | The software expects to receive a data set ready signal during the login process. If it does not, you will receive one of the following error messages:
> | (ALOGIN) eopen of port 0 failed, rc = 0x85. Processing stopped. (LOGIN) FATAL ERROR:System error; login.c, 84, 133. Processing stopped.
> Solution | This problem is most often seen with Hayes modems. Use the -i option to bypass the search for the DSR signal.
> Problem | When you attempt to log into the voice mail system using an invalid argument or option with the login command (for example, an invalid delete or password), the command will fail.
> Solution | When you log into the voice mail system, use the -v option with the login command. Detailed transfer statistics of the login command status and the voice mail system connect responses will then be written to the screen. These statistics will help you determine the solution to this problem.
#### Top of page

| Search This CD Index Contact Us
| © 2002-2007 Avaya Inc. All rights reserved.